Handling interrupts when virtual machines have direct access to a hardware device

ABSTRACT

In virtualized computer system in which a guest operating system runs on a virtual machine of a virtualized computer system and has direct access to a hardware device coupled to the virtualized computer system via a communication interface, a computer-implemented method of handling interrupts from the hardware device to the guest operating system includes: (a) receiving a physical interrupt from the hardware device on a shared interrupt line of an interrupt controller; (b) masking the shared interrupt line of the interrupt controller; (c) generating a virtual interrupt corresponding to the physical interrupt to the guest operating system; and (d) the guest operating system executing an interrupt service routine.

This application claims the benefit of U.S. Provisional Application No.60/939,819, filed May 23, 2007, which provisional application isincorporated herein by reference in its entirety.

CROSS-REFERENCE TO RELATED APPLICATION

This application is related to U.S. patent application Ser. No.12/124,586, filed May 21, 2008, entitled “Direct Access to a HardwareDevice for Virtual Machines of a Virtualized Computer System,”.

FIELD OF THE INVENTION

One or more embodiments of the present invention relate to virtualizedcomputer systems, and, in particular, to a system and method forproviding a guest operating system (O/S) in a virtualized computersystem with direct access to a hardware device.

BACKGROUND General Computer System with a PCI Bus

FIG. 1A shows a general computer system that comprises system hardware30. System hardware 30 may be a conventional computer system, such as apersonal computer based on the widespread “x86” processor architecturefrom Intel Corporation of Santa Clara, Calif., and system hardware 30may include conventional components, such as one or more processors,system memory, and a local disk. System memory is typically some form ofhigh-speed RAM (Random Access Memory), whereas the disk (one or more) istypically a non-volatile, mass storage device. System hardware 30 mayalso include other conventional components such as a memory managementunit (MMU), various registers, and various input/output (I/O) devices.

As further shown in FIG. 1A, system hardware 30 includes CentralProcessing Unit 32 (CPU 32), host/PCI bridge 36, system memory 40, SmallComputer System Interface (SCSI) Host Bus Adapter (HBA) card 44 (SCSIHBA 44), Network Interface Card 46 (NIC 46), and graphics adapter 48,each of which may be conventional devices. As further shown in FIG. 1A:(a) CPU 32 is connected to host/PCI bridge 36 by CPU local bus 34 in aconventional manner; (b) system memory 40 is connected to host/PCIbridge 36 by memory bus 38 in a conventional manner; and (c) SCSI HBA44, NIC 46 and graphics adapter 48 are connected to host/PCI bridge 36by Peripheral Component Interconnect bus 42 (PCI bus 42) in aconventional manner. As further shown in FIG. 1A, graphics adapter 48 isconnected to conventional video monitor 62 in a conventional manner; andNIC 46 is connected to one or more conventional data networks 60 in aconventional manner. Networks 60 may be based on Ethernet technology,for example, and the networks may use the Internet Protocol and theTransmission Control Protocol (TCP/IP), for example. Also, SCSI HBA 44supports SCSI bus 50 in a conventional manner, and various devices maybe connected to SCSI bus 50 in a conventional manner. For example, FIG.1A shows SCSI disk 52 and tape storage device 54 connected to SCSI bus50. Other devices may also be connected to SCSI bus 50. SCSI HBA 44 maybe an Adaptec Ultra320 or Ultra160 SCSI PCI HBA from Adaptec, Inc., oran LSI Logic Fusion-MPT SCSI HBA from LSI Logic Corporation, forexample.

Computer systems generally have system level software and applicationsoftware executing on the system hardware. As shown in FIG. 1A, systemsoftware 21 (system S/W 21) is executing on system hardware 30. Asfurther shown in FIG. 1A, system software 21 includes operating system(OS) 20 and system BIOS (Basic Input/Output System) 22, although othersystem level software configurations are also possible. OS 20 may be aconventional OS for system hardware 30, such as a Windows OS fromMicrosoft Corp. or a Linux OS, for example. A Windows OS from MicrosoftCorp. may be a Windows Vista OS, Windows XP OS or a Windows 2000 OS, forexample, while a Linux OS may be a distribution from Novell, Inc. (SUSELinux), Mandrakesoft S.A. or Red Hat, Inc. OS 20 may include a set ofdrivers 24, some of which may be packaged with OS 20, and some of whichmay be separately loaded onto system hardware 30. Drivers 24 may providea variety of functions, including supporting interfaces with SCSI HBA44, NIC 46 and graphics adapter 48. Drivers 24 may also be conventionalfor system hardware 30 and OS 20. System BIOS 22 may also beconventional for system hardware 30. Finally, FIG. 1A shows a set of oneor more applications 10 (APPS 10) executing on system hardware 30. APPS10 may also be conventional for system hardware 30 and OS 20.

The computer system shown in FIG. 1A may be initialized in aconventional manner. Thus, when the computer system is powered up, orrestarted, system BIOS 22 and/or OS 20, or, more generally, systemsoftware 21, may detect and configure various aspects of system hardware30 in a conventional manner. For example, system software 21 may detectand configure devices interacting with PCI bus 42 (i.e., PCI devices) ina conventional manner, including, in particular, SCSI HBA 44. A personof skill in the art will understand how such devices are detected andconfigured. Briefly, a PCI device typically implements at least 16“doublewords” of standard configuration registers, where there are 32bits in a “doubleword.” System software 21 attempts to access theconfiguration registers of PCI devices at each possible location on PCIbus 42, including each PCI slot in system hardware 30. Attempting toaccess the configuration registers enables system software 21 todetermine whether there is a PCI device at each possible location on PCIbus 42, as well as the function or functions that are implemented ineach PCI device. System software 21 can then obtain additionalinformation from the configuration registers of each PCI device, andconfigure such devices appropriately.

If a PCI device implements an extended ROM (Read Only Memory), which mayalso be referred to as a device ROM or option ROM, then system software21 typically copies a code image from the ROM on the PCI device intosystem memory 40 (for example, RAM) within system hardware 30. Aninitialization module within the code image is typically executed aspart of the initialization process, and this may further initialize thePCI device and/or other devices connected to the PCI device. Referringagain to FIG. 1A, during the initialization process, system software 21attempts to access the configuration registers of PCI devices at eachpossible location on PCI bus 42, and detects graphics adapter 48, NIC 46and SCSI HBA 44. System software 21 determines the functions implementedin each of these devices, along with other relevant information, andinitializes each of the devices appropriately. SCSI HBA 44 typicallyincludes an extended ROM which contains an initialization module that,when executed, initializes SCSI bus 50 and devices connected to SCSI bus50, including SCSI DISK 52 and tape storage device 54. Theinitialization of PCI bus 42; devices connected to PCI bus 42, includinggraphics adapter 48, NIC 46, and SCSI HBA 44; SCSI bus 50; and devicesconnected to SCSI bus 50, including SCSI disk 52 and tape storage device54, may all be performed in a conventional manner.

FIG. 1B shows a set of PCI configuration registers 45 for SCSI HBA 44.As described above, during initialization, system software 21 accessesPCI configuration registers 45 to detect the presence of SCSI HBA 44 andto initialize SCSI HBA 44. PCI configuration registers 45 may also beaccessed by system software 21 or by other software running on systemhardware 30, at other times, for other purposes. FIG. 1B shows, morespecifically, Vendor ID (Identifier) register 45A, Device ID register45B, Command register 45C, Status register 45D, Revision ID register45E, Class Code register 45F, Cache Line Size register 45G, LatencyTimer register 45H, Header Type register 45I, Built-In Self-Test (BIST)register 45J, Base Address 0 register 45K, Base Address 1 register 45L,Base Address 2 register 45M, Base Address 3 register 45N, Base Address 4register 45O, Base Address 5 register 45P, CardBus Card InformationStructure (CIS) Pointer register 45Q, Subsystem Vendor ID register 45R,Subsystem ID register 45S, Expansion ROM Base Address register 45T,first reserved register 45U, second reserved register 45V, InterruptLine register 45W, Interrupt Pin register 45X, Min_Gnt register 45Y, andMax_Lat register 45Z. Depending on the particular SCSI HBA used,however, one or more of these registers may not be implemented. Theformat, function and use of these configuration registers, includingspecific information regarding how to access these configurationregisters, are well understood in the art and need not be describedfurther.

FIG. 1B also shows PCI extended configuration space 45AA, which mayinclude a set of Device-capability Registers. The formats of theseDevice-capability registers are standard, although devices fromdifferent vendors may advertise different capabilities. For example, thecontent of Device-capability Registers 45AA may differ between multipleSCSI HBA devices from different vendors. Finally, the format and contentof these registers may even vary for different models of the same typeof device from a single vendor.

Referring again to the initialization process, when system software 21is initializing devices on PCI bus 42, system software 21 reads one ormore of PCI configuration registers 45 of SCSI HBA 44, such as Vendor IDregister 45A and Device ID register 45B, and determines the presence andtype of device SCSI HBA 44 is. System software 21 then reads additionalconfiguration registers, and configures SCSI HBA 44 appropriately, bywriting certain values to some of configuration registers 45. Inparticular, system software 21 reads one or more of Base AddressRegisters (BARs) 45K, 45L, 45M, 45N, 450, and 45P to determine how manyregions and how many blocks of memory and/or I/O address space SCSI HBA44 requires, and system software 21 writes to one or more of the BaseAddress registers to specify address range(s) to satisfy theserequirements.

As an example, suppose that Base Address 0 register (BAR 0) 45Kindicates that SCSI HBA 44 requires a first number of blocks of I/Oaddress space and that Base Address 1 (BAR 1) register 45L indicatesthat SCSI HBA 44 requires a second number of blocks of memory addressspace. This situation is illustrated in FIG. 1C, showing configurationaddress space 70, I/O address space 72, and memory address space 74.System software 21 may write to Base Address 0 register (BAR 0) 45K andspecify I/O region 72A within I/O address space 72, I/O region 72Ahaving a first number of blocks; and system software 21 may write toBase Address 1 register (BAR 1) 45L and specify memory region 74A withinmemory address space 74, memory region 74A having a second number ofblocks. PCI configuration registers 45 of SCSI HBA 44 may be accessedwithin configuration address space 70. As shown in FIG. 1C, Base Address0 register 45K contains a pointer to I/O region 72A within I/O addressspace 72, and Base Address 1 register 45L contains a pointer to memoryregion 74A within memory address space 74.

Subsequently, system software 21 may determine that SCSI HBA 44 containsan extended ROM, and system software 21 creates a copy of the ROM codein memory and executes the code in a conventional manner. Extended ROMcode from SCSI HBA 44 initializes SCSI bus 50 and devices connected toSCSI bus 50, including SCSI DISK 52 and tape storage device 54,generally in a conventional manner.

After the computer system shown in FIG. 1A is initialized, including thePCI devices on PCI bus 42, configuration registers in the respective PCIdevices may be accessed on an ongoing basis to interact with the PCIdevices and to utilize functions implemented by the PCI devices. Inparticular, PCI configuration registers 45 in SCSI HBA 44 may beaccessed to determine which SCI HBA is connected to PCI bus 42, todetermine characteristics of PCI devices connected to SCSI bus 50, andto interface with the PCI devices on SCSI bus 50, all in a conventionalmanner. For example, configuration registers 45 of SCSI HBA 44 may beused to eventually determine that SCSI DISK 52 and tape storage device54 are connected to the SCSI bus 50, and to determine variouscharacteristics of these storage devices.

Also, after the computer system shown in FIG. 1A is initialized,software executing on system hardware 30 may perform I/O transfers toand from devices on PCI bus 42, namely I/O writes to devices on PCI bus42 and I/O reads from devices on PCI bus 42. These I/O transfers areperformed in a conventional manner using the memory regions and/or I/Oregions specified in the Base Address registers of a PCI device. TheseI/O transfers may be DMA (Direct Memory Access) transfers from thedevices or they may be non-DMA transfers. In the case of SCSI HBA 44,software executing on system hardware 30 may perform I/O transfers toand from devices on SCSI bus 50, through SCSI HBA 44, in a conventionmanner. For example, such I/O transfers through SCSI HBA 44 may be usedto write data to SCSI DISK 52 or to read data from SCSI DISK 52, both ina conventional manner. For an I/O write to SCSI DISK 52, CPU 32 conveysdata to SCSI HBA 44, which then sends the data across SCSI bus 50 toSCSI DISK 52; while, for an I/O read from SCSI DISK 52, SCSI DISK 52transmits data across SCSI bus 50 to SCSI HBA 44, and SCSI HBA 44 sendsthe data to CPU 32. In the example shown in FIG. 1C, such I/O transfersmay be performed using I/O region 72A or memory region 74A. Such I/Otransfers may be performed, for example, by SCSI driver 24 on behalf ofapplication software in one of applications 10.

These I/O transfers to and from PCI devices may be further broken downinto (a) transactions initiated by CPU 32 and (b) transactions initiatedby PCI devices. Non-DMA I/O transfers involve only CPU-initiatedtransactions. For a non-DMA write, CPU 32 initiates the transfer, writesdata to the PCI device, and the PCI device receives the data, all in thesame transaction. For a non-DMA read, CPU 32 initiates the transfer andthe PCI device retrieves the data and provides it to CPU 32, again allin the same transaction. Thus, non-DMA I/O transfers may be consideredsimple CPU accesses to the PCI devices.

DMA I/O transfers, in contrast, involve transactions initiated by thePCI devices. For a DMA write transfer, CPU 32 first writes data to amemory region without any involvement by a PCI device. CPU 32 theninitiates the DMA transfer in a first transaction, involving a CPUaccess to the PCI device. Subsequently, the PCI device reads the datafrom the memory region in a second transaction. This second transactionmay be considered a “DMA operation” by the PCI device. For a DMA readoperation, CPU 32 initiates the DMA transfer in a first transaction,involving a CPU access to the PCI device. The PCI device then retrievesthe data and writes it into a memory region in a second transaction,which may also be considered a “DMA operation” by the PCI device. Next,the CPU reads the data from the memory region without any furtherinvolvement by the PCI device. Thus, DMA I/O transfers to and from a PCIdevice generally involves both a CPU access to the PCI device and a DMAoperation by the PCI device.

In addition to accesses to configuration registers of PCI devices andI/O transfers to and from PCI devices, PCI devices also typicallygenerate interrupts to CPU 32 for various reasons, such as, completionof a DMA transfer. Such interrupts may be generated and handled in aconventional manner.

In summary, there are four general types of transactions that occurbetween CPU 32 and a PCI device, such as SCSI HBA 44. A firsttransaction type (“a configuration transaction”) involves an access byCPU 32 to configuration registers of the PCI device, such as PCIconfiguration registers 45 of SCSI HBA 44. A second transaction type(“an I/O transaction”) involves an access by CPU 32 to the PCI device,through the memory and/or I/O region(s) specified by the Base Addressregisters of the PCI device, such as I/O region 72A or memory region 74Afor SCSI HBA 44 in the example shown in FIG. 1C. A third transactiontype (“a DMA operation”) involves a DMA operation by the PCI device,which involves a read from or a write to a memory region specified by aBase Address register of the PCI device, such as memory region 74A forSCSI HBA 44 in the example shown in FIG. 1C. A fourth transaction type(“an interrupt”) involves an interrupt from the PCI device to CPU 32,such as upon completion of a DMA transfer.

General Virtualized Computer System

As is well known in the field of computer science, a virtual machine(VM) is an abstraction—a “virtualization”—of an actual physical computersystem. FIG. 2A shows one possible arrangement of a computer system thatimplements virtualization. As shown in FIG. 2A, one or more VMs 300, or“guests,” are installed on a “host platform,” or simply “host,” whichincludes system hardware, and one or more layers or co-residentcomponents comprising system-level software, such as an operating systemor similar kernel, or a virtual machine monitor or hypervisor (seebelow), or some combination of these. The system hardware typicallyincludes one or more processors, memory, some form of mass storage, andvarious other devices.

The computer system shown in FIG. 2A has the same system hardware 30 asis shown in FIG. 1A and described above. Thus, system hardware 30 shownin FIG. 2A also includes CPU 32, host/PCI bridge 36, system memory 40,SCSI HBA 44, NIC 46, and graphics adapter 48 shown in FIG. 1A, althoughthese components are not illustrated in FIG. 2A for simplicity. As alsoillustrated in FIG. 1A, but not in FIG. 2A, CPU 32 is connected tohost/PCI bridge 36 by CPU local bus 34, in a conventional manner; systemmemory 40 is connected to host/PCI bridge 36 by memory bus 38, in aconventional manner; and SCSI HBA 44, NIC 46 and graphics adapter 48 areconnected to host/PCI bridge 36 by PCI bus 42, in a conventional manner.

FIG. 2A also shows the same video monitor 62, the same networks 60 andthe same SCSI bus 50 as are shown in FIG. 1A, along with the same SCSIDISK 52 and the same tape storage device 54, which are again shown asbeing connected to SCSI bus 50. Other devices may also be connected toSCSI bus 50. Thus, graphics adapter 48 (not shown in FIG. 2A) isconnected to video monitor 62 in a conventional manner; NIC 46 (notshown in FIG. 2A) is connected to data networks 60 in a conventionalmanner; and SCSI HBA 44 (not shown in FIG. 2A) supports SCSI bus 50 in aconventional manner.

Guest system software runs on VMs 300. Each virtual machine monitor 200(VMM 200) (or a software layer where VM 300 and VMM 200 overlap)typically includes virtual system hardware 330. Virtual system hardware330 typically includes at least one virtual CPU, some virtual memory,and one or more virtual devices. All of the virtual hardware componentsof the VM may be implemented in software using known techniques toemulate the corresponding physical components.

FIG. 2B shows aspects of virtual system hardware 330. For the examplevirtual computer systems of FIGS. 2A and 2B, virtual system hardware 330is functionally similar to underlying physical system hardware 30,although, for other virtual computer systems, the virtual systemhardware may be quite different from the underlying physical systemhardware. Thus, FIG. 2B shows processor (CPU or Central Processing Unit)332, host/PCI bridge 336, system memory 340, SCSI HBA 344, NIC 346, andgraphics adapter 348, each of which may be implemented as conventionaldevices that are substantially similar to their corresponding devices inunderlying physical hardware 30. As shown in FIG. 2B, CPU 332 appears tobe connected to host/PCI bridge 336 in a conventional manner, as if byCPU local bus 334; system memory 340 appears to be connected to host/PCIbridge 336 in a conventional manner, as if by memory bus 338; and SCSIHBA 344, NIC 346 and graphics adapter 348 appear to be connected tohost/PCI bridge 336 in a conventional manner, as if by PCI bus 342.

As further shown in FIG. 2B, graphics adapter 348 appears to beconnected to conventional video monitor 362 in a conventional manner;NIC 346 appears to be connected to one or more conventional datanetworks 360 in a conventional manner; SCSI HBA 344 appears to supportSCSI bus 350 in a conventional manner; and virtual disk 352 and tapestorage device 354 appear to be connected to SCSI bus 350, in aconventional manner. Virtual disk 352 typically represents a portion ofSCSI DISK 52. It is common for virtualization software to provide guestsoftware within a VM with access to some portion of a SCSI DISK,including possibly a complete Logical Unit Number (LUN), multiplecomplete LUNs, some portion of a LUN, or even some combination ofcomplete and/or partial LUNs. Whatever portion of the SCSI DISK is madeavailable for use by the guest software, within the VM the portion isoften presented to the guest software in the form of one or morecomplete virtual disks. Methods for virtualizing a portion of a SCSIDISK as one or more virtual disks are known in the art. Other thanpresenting a portion of SCSI DISK 52 as a complete virtual disk 352, allof the virtual devices illustrated in FIG. 2B may be emulated in such amanner that they are functionally similar to the corresponding physicaldevices illustrated in FIG. 1A, or, alternatively, the virtual devicesmay be emulated so as to make them quite different from the underlyingphysical devices.

Guest system software in VMs 300 of FIG. 2A includes OS 320, including aset of drivers 324, and system BIOS 322. FIG. 2A also shows one or moreapplications 310 running within VMs 300. OS 320 may be substantially thesame as OS 20 of FIG. 1A, or it may be substantially different; drivers324 may be substantially the same as drivers 24 of FIG. 1A, or they maybe substantially different; system BIOS 322 may be substantially thesame as system BIOS 22 of FIG. 1A, or it may be substantially different;and applications 310 may be substantially the same as applications 10 ofFIG. 1A, or they may be substantially different. Also, each of thesesoftware units may be substantially the same between different VMs, assuggested in FIG. 2A, or they may be substantially different.

Note that a single VM may be configured with more than one virtualizedprocessor. To permit computer systems to scale to larger numbers ofconcurrent threads, systems with multiple CPUs have been developed. Forexample, symmetric multi-processor (SMP) systems are available asextensions of the PC platform and from other vendors. Essentially, anSMP system is a hardware platform that connects multiple processors to ashared main memory and shared I/O devices. Virtual machines may also beconfigured as SMP VMs. In addition, another configuration is found in aso-called “multi-core” architecture, in which more than one physical CPUis fabricated on a single chip, with its own set of functional units(such as a floating-point unit and an arithmetic/logic unit ALU), and inwhich threads can execute independently; multi-core processors typicallyshare only limited resources, such as some cache. In further addition, atechnique that provides for simultaneous execution of multiple threadsis referred to as “simultaneous multi-threading,” in which more than onelogical CPU (hardware thread) operates simultaneously on a single chip,but in which the logical CPUs flexibly share some resource such ascaches, buffers, functional units, etc.

Applications 310 running on a VM function as they would if run on a“real” computer, even though the applications are running at leastpartially indirectly, that is via guest OS 320 and virtual processor(s).Executable files are accessed by the guest OS from a virtual disk orvirtual memory, which will be portions of an actual physical disk ormemory allocated to that VM. Once an application is installed within aVM, the guest OS retrieves files from the virtual disk just as if thefiles had been pre-stored as the result of a conventional installationof the application. The design and operation of virtual machines arewell known in the field of computer science.

Some interface is generally required between guest software within a VMand various hardware components and devices in an underlying hardwareplatform. This interface—which may be referred to generally as“virtualization software”—may include one or more software componentsand/or layers, possibly including one or more of the software componentsknown in the field of virtual machine technology as “virtual machinemonitors” (VMMs), “hypervisors,” or virtualization “kernels.” Becausevirtualization terminology has evolved over time and has not yet becomefully standardized, these terms do not always provide clear distinctionsbetween the software layers and components to which they refer. Forexample, the term “hypervisor” is often used to describe both a VMM anda kernel together, either as separate but cooperating components or withone or more VMMs incorporated wholly or partially into the kernelitself; however, the term “hypervisor” is sometimes used instead to meansome variant of a VMM alone, which interfaces with some other softwarelayer(s) or component(s) to support the virtualization. Moreover, insome systems, some virtualization code is included in at least one“superior” VM to facilitate the operations of other VMs. Furthermore,specific software support for VMs may be included in a host OS itself.

FIG. 2A shows virtual machine monitors 200 that appear as separateentities from other components of the virtualization software.Furthermore, some software components are shown and described as beingwithin a “virtualization layer” located logically between all virtualmachines and the underlying hardware platform and/or system-level hostsoftware. This virtualization layer can be considered part of theoverall virtualization software, although it would be possible toimplement at least part of this layer in specialized hardware.

Various virtualized hardware components may be considered to be part ofVMM 200 for the sake of conceptual simplicity. In actuality, these“components” are usually implemented as software emulations by virtualdevice emulators 202 included in the VMMs. One advantage of such anarrangement is that the VMMs may (but need not) be set up to expose“generic” devices, which facilitate VM migration and hardwareplatform-independence.

Different systems may implement virtualization to different degrees—theterm “virtualization” generally relates to a spectrum of definitionsrather than to a bright line, and often reflects a design choice withrespect to a trade-off between speed and efficiency on the one hand andisolation and universality on the other hand. For example, the term“full virtualization” is sometimes used to denote a system in which nosoftware components of any form are included in a guest other than thosethat would be found in a non-virtualized computer; thus, a guest OScould be an off-the-shelf, commercially available OS with no componentsincluded specifically to support use in a virtualized environment.

In contrast, term, which has yet to achieve a universally accepteddefinition, is that of “para-virtualization.” As the term implies, a“para-virtualized” system is not “fully” virtualized, but rather a guestis configured in some way to provide certain features that facilitatevirtualization. For example, a guest in some para-virtualized systems isdesigned to avoid hard-to-virtualize operations and configurations, suchas by avoiding certain privileged instructions, certain memory addressranges, etc. As another example, many para-virtualized systems includean interface within a guest that enables explicit calls to othercomponents of the virtualization software.

For some, the term para-virtualization implies that a guest OS (inparticular, its kernel) is specifically designed to support such aninterface. According to such a view, having, for example, anoff-the-shelf version of Microsoft Windows XP as a guest OS would not beconsistent with the notion of para-virtualization. Others define theterm para-virtualization more broadly to include any guest OS with anycode that is specifically intended to provide information directly toany other component of the virtualization software. According to thisview, loading a module such as a driver designed to communicate withother virtualization components renders the system para-virtualized,even if the guest OS, as such, is an off-the-shelf, commerciallyavailable OS not specifically designed to support a virtualized computersystem.

In addition to the sometimes fuzzy distinction between full and partial(para-) virtualization, two arrangements of intermediate system-levelsoftware layer(s) are in general use—a “hosted” configuration and anon-hosted configuration (which is shown in FIG. 2A). In a hostedvirtualized computer system, an existing, general-purpose operatingsystem forms a “host” OS that is used to perform certain input/output(I/O) operations, alongside and sometimes at the request of the VMM. AWorkstation virtualization product of VMware, Inc., of Palo Alto,Calif., is an example of a hosted, virtualized computer system, which isalso explained in U.S. Pat. No. 6,496,847 (Bugnion, et al., “System andMethod for Virtualizing Computer Systems,” 17 Dec. 2002).

As illustrated in FIG. 2A, in many cases, it may be beneficial to deployVMMs on top of a software layer—kernel 100 (also referred to as VMKernel100)—constructed specifically to provide efficient support for VMs. Thisconfiguration is frequently referred to as being “non-hosted.” Comparedwith a system in which VMMs run directly on the hardware platform, useof a kernel offers greater modularity and facilitates provision ofservices that extend across multiple virtual machines. Thus, the VMM mayinclude resource manager 102, for example, for managing resources acrossmultiple virtual machines. Compared with a hosted deployment, a kernelmay offer greater performance because it can be co-developed with theVMM and be optimized for the characteristics of a workload consistingprimarily of VMs/VMMs. Kernel 100 may also handle other applicationsrunning on it that can be separately scheduled, as well as a consoleoperating system that, in some architectures, is used to boot the systemand facilitate certain user interactions with the virtualizationsoftware.

Note that VMkernel 100 shown in FIG. 2A is not the same as a kernel thatwill be within guest OS 320—as is well known, every operating system hasits own kernel. Note also that kernel 100 is part of the “host” platformof the VM/VMM as defined above even though the configuration shown inFIG. 2A is commonly termed “non-hosted;” moreover, VMkernel 100 is partof the host and part of the virtualization software or “hypervisor.” Thedifference in terminology is one of perspective and definitions that arestill evolving in the art of virtualization.

One of device emulators 202 emulates virtual SCSI HBA 344, usingphysical SCSI HBA 44 to actually perform data transfers, etc. Thus, forexample, if guest software attempts to read data from what it sees asvirtual disk 352, SCSI device driver 324 typically interacts with whatit sees as SCSI HBA 344 to request the data. Device emulator 202responds to SCSI device driver 324, and causes physical SCSI HBA 44 toread the requested data from an appropriate location within physicalSCSI DISK 52. Device emulator 202 typically has to translate a SCSI I/Ooperation initiated by SCSI device driver 324 into a corresponding SCSIoperation issued to SCSI HBA 44, and finally onto SCSI DISK 52. Methodsfor emulating disks and SCSI DISKs, and for translating disk operationsduring such emulations, are known in the art.

During the operation of VM 300, SCSI device driver 324 typicallyinteracts with virtual SCSI HBA 344 just as if it were a real, physicalSCSI HBA. At different times, SCSI device driver 324 may exercisedifferent functionality of virtual SCSI HBA 344, and so device emulator202 typically must emulate all the functionality of the virtual SCSIHBA. However, device emulator 202 does not necessarily have to emulateall of the functionality of physical SCSI HBA 44. Virtual SCSI HBA 344emulated by device emulator 202 may be substantially different fromphysical SCSI HBA 44. For example, virtual SCSI HBA 344 may be more of ageneric SCSI HBA, implementing less functionality than physical SCSI HBA44. Nonetheless, device emulator 202 typically emulates all thefunctionality of some SCSI HBA. Thus, for example, SCSI driver 324 mayattempt to access the PCI configuration registers of virtual SCSI HBA344, and device emulator 202 typically must emulate the functionality ofthe configuration registers.

FIG. 2C illustrates a set of emulated or virtual PCI configurationregisters 345. Specifically, FIG. 2C shows Vendor ID register 345A,Device ID register 345B, Command register 345C, Status register 345D,Revision ID register 345E, Class Code register 345F, Cache Line Sizeregister 345G, Latency Timer register 345H, Header Type register 345I,BIST register 345J, Base Address 0 register 345K, Base Address 1register 345L, Base Address 2 register 345M, Base Address 3 register345N, Base Address 4 register 345O, Base Address 5 register 345P,CardBus CIS Pointer register 345Q, Subsystem Vendor ID register 345R,Subsystem ID register 345S, Expansion ROM Base Address register 345T,first reserved register 345U, second reserved register 345V, InterruptLine register 345W, Interrupt Pin register 345X, Min_Gnt register 345Y,and Max_Lat register 345Z. As with physical SCSI HBA 44, one or more ofthese registers may not be implemented, depending on the particular SCSIHBA that is emulated as virtual SCSI HBA 344. Also, the registers thatare implemented in virtual PCI configuration registers 345 may differfrom the registers that are implemented in physical PCI configurationregisters 45. FIG. 2C also shows Virtual PCI Extended ConfigurationSpace (including a set of Device-Specific Registers) 345AA.

The contents of virtual PCI configuration registers 345 are generallydifferent from the contents of physical PCI configuration registers 45,and the format of Device-Specific Registers 345AA may be different fromthe format of Device-Specific Registers 45AA, typically depending moreon the design and implementation of the virtualization software than onthe characteristics of physical SCSI HBA 44 or any connected SCSIdevices. For example, the virtualization software may be implemented soas to allow a VM to be migrated from one physical computer to anotherphysical computer. A VM may be migrated from a first physical computerto a second physical computer by copying VM state and memory stateinformation for the VM from the first computer to the second computer,and restarting the VM on the second physical computer. Migration of VMsis more practical and efficient if the VMs include more generic virtualhardware that is independent of the physical hardware of the underlyingcomputer system. Thus, virtual PCI configuration registers 345 for suchan implementation would reflect the generic virtual hardware, instead ofthe underlying physical hardware of the computer on which the VM iscurrently running. Thus, there may be no, or only limited, correlationbetween the contents of virtual PCI configuration registers 345 andphysical PCI configuration registers 45, and between the format ofvirtual Device-Specific Registers 345AA and physical Device-SpecificRegisters 45AA.

FIG. 2D illustrates configuration address space 370 corresponding tovirtual PCI configuration register 345. As an example, suppose that BaseAddress 0 register (BAR 0) 345K indicates that SCSI HBA 344 requires afirst number of blocks of I/O address space and that Base Address 1 (BAR1) register 345L indicates that SCSI HBA 344 requires a second number ofblocks of memory address space. As shown in FIG. 2D, guest OS 320 maywrite to Base Address 0 register (BAR 0) 345K and specify I/O region372A within I/O address space 372, I/O region 372A having the firstnumber of blocks; and guest OS 320 may write to Base Address 1 register(BAR 1) 345L and specify memory region 374A within memory address space374, memory region 374A having the second number of blocks. PCIconfiguration registers 345 of SCSI HBA 344 may be accessed withinconfiguration address space 370. Base Address 0 register 345K contains apointer to I/O region 372A within I/O address space 372, and BaseAddress 1 register 345L contains a pointer to memory region 374A withinmemory address space 374.

Subsequently, guest OS 320 may determine that virtual SCSI HBA 344contains an extended ROM, and guest OS 320 creates a copy of the ROMcode in memory and executes the code in a conventional manner. Theextended ROM code from virtual SCSI HBA 344 initializes virtual SCSI bus350 and the devices connected to virtual SCSI bus 350, including virtualSCSI DISK 352 and virtual tape storage device 354, generally in aconventional manner.

In general, conventional virtualized computer systems do not allow guestOS 320 to control the actual physical hardware devices. For example,guest OS 320 running on VM 300 would not have direct access to SCSI HBA44 or SCSI disk 52. This is because virtualized computer systems havevirtualization software such as VMM 200 and VMKernel 100 coordinate eachVM's access to the physical devices to allow multiple VMs 300 to run onshared system H/W 30 without conflict.

SUMMARY

One or more embodiments of the present invention include acomputer-implemented method for a guest operating system running on avirtual machine in a virtualized computer system to handle interrupts.In particular, in accordance with one embodiment, in virtualizedcomputer system in which a guest operating system runs on a virtualmachine of a virtualized computer system and has direct access to ahardware device coupled to the virtualized computer system via acommunication interface, a computer-implemented method of handlinginterrupts from the hardware device to the guest operating systemcomprises: (a) receiving a physical interrupt from the hardware deviceon a shared interrupt line of an interrupt controller; (b) masking theshared interrupt line of the interrupt controller; (c) generating avirtual interrupt corresponding to the physical interrupt to the guestoperating system; and (d) the guest operating system executing aninterrupt service routine.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a general, non-virtualized computer system having aPCI bus and a SCSI HBA PCI device, supporting a SCSI bus.

FIG. 1B illustrates a set of PCI configuration registers for the SCSIHBA PCI device of FIG. 1A.

FIG. 1C illustrates a configuration address space, an I/O address spaceand a memory address space related to the SCSI HBA PCI device of FIG.1A.

FIG. 2A illustrates the main components of a general, kernel-based,virtual computer system, in which the physical system hardware includesa PCI bus and a SCSI HBA PCI device, supporting a SCSI bus.

FIG. 2B illustrates a virtual system hardware for the virtual machinesof FIG. 2A, including a virtual PCI bus and a virtual SCSI HBA PCIdevice, supporting a virtual SCSI bus.

FIG. 2C illustrates a set of virtual PCI configuration registers for thevirtual SCSI HBA PCI device of FIG. 2B.

FIG. 2D illustrates a configuration address space, an I/O address spaceand a memory address space related to the virtual SCSI HBA PCI device ofFIG. 2B.

FIG. 3A illustrates an embodiment of the present invention in ageneralized, kernel-based, virtual computer system, in which thephysical system hardware includes a PCI bus and a SCSI HBA PCI device,supporting a SCSI bus.

FIG. 3B illustrates a virtual system hardware for the virtual machine ofFIG. 3A, including a PCI passthrough SCSI disk, a virtual PCI bus and avirtual SCSI HBA PCI device, supporting a virtual SCSI bus, according toone embodiment of the present invention.

FIG. 3C illustrates a set of virtual PCI configuration registers for thePCI passthrough SCSI disk, according to one embodiment of the presentinvention.

FIG. 4A is an interaction diagram illustrating how the PCI passthroughdevice is created and used in non-trap mode, according to one embodimentof the present invention.

FIG. 4B is an interaction diagram illustrating how the PCI passthroughdevice is created and used in trap mode, according to one embodiment ofthe present invention.

FIG. 5A is an interaction diagram illustrating I/O operation in the PCIpassthrough device using callbacks for I/O mapped accesses, according toone embodiment of the present invention.

FIG. 5B is an interaction diagram illustrating I/O operation in the PCIpassthrough device using driver change, according to one embodiment ofthe present invention.

FIG. 5C is an interaction diagram illustrating I/O operation in the PCIpassthrough device using on-demand mapping with an I/O MMU (Input/OutputMemory Management Unit), according to one embodiment of the presentinvention.

FIG. 5D is an interaction diagram illustrating I/O operation in the PCIpassthrough device using identity mapping, according to one embodimentof the present invention.

FIG. 6 is an interaction diagram illustrating interrupt handling in thePCI passthrough device using physical I/O APIC (Advanced ProgrammableInterrupt Controller), according to one embodiment of the presentinvention.

FIG. 7A is an interaction diagram illustrating interrupt handling in thePCI passthrough device using a physical MSI/MSI-X device with virtualI/O APIC, according to one embodiment of the present invention.

FIG. 7B is an interaction diagram illustrating interrupt handling in thePCI passthrough device using a physical MSI/MSI-X device with virtualMSI/MSI-X, according to one embodiment of the present invention.

DETAILED DESCRIPTION

The inventors have determined that, at least sometimes, there is a needfor a virtual machine (VM) in a virtualized computer system, forexample, a guest operating system (OS) running on a VM to have directaccess to physical hardware devices, such as, for example and withoutlimitation, physical PCI devices. For example, and without limitation,direct access to physical hardware devices may be needed for better I/O(Input/Output) performance. As a further example, with direct access tophysical hardware devices, a VM may be able to manage the physicalhardware devices directly, and backup physical hardware devices such asSCSI disks directly. In addition, by trapping port and memory mappedoperations to/from the physical hardware devices that are exposed to theVM for direct access, it is possible to study the behavior of thephysical hardware devices from the VM as a debugging mechanism.

One or more embodiments of the present invention relate to providinglimited, direct access to a physical device from within a computingenvironment that is at least partially virtualized. One or moreembodiments of the present invention may be implemented in a widevariety of physical computer systems, which physical computer systemshave a wide variety of hardware platforms and configurations, and a widevariety of software platforms and configurations. In particular, one ormore embodiments of the present invention may be implemented in computersystems having varying degrees and/or types of virtualization with VMshaving any number of physical and/or logical virtualized processors,including fully virtualized computer systems (both hosted and non-hostedvirtualized computer systems), partially virtualized systems (regardlessof the degree of virtualization), i.e., so-called para-virtualizedcomputer systems, and a wide variety of other types of virtual computersystems, including virtual computer systems in which a virtualizedhardware platform is substantially the same as or substantiallydifferent from an underlying physical hardware platform. In addition,one or more embodiments of the present invention may also be implementedto provide limited, direct access to a wide variety of physical devicesthat may interface with a physical computer system in a variety of ways.

FIG. 3A illustrates an embodiment of the present invention in ageneralized, kernel-based, virtual computer system, in which thephysical system hardware includes a PCI bus and a SCSI HBA PCI device,supporting a SCSI bus. The computer system shown in FIG. 3A has the samesystem hardware 30 as that shown in FIGS. 1A and 2A, and as is describedabove. Thus, system hardware 30 of FIG. 3A also includes CPU 32,host/PCI bridge 36, system memory 40, SCSI HBA 44, NIC 46, and graphicsadapter 48 of FIG. 1A, although these devices are not illustrated inFIG. 3A for simplicity. As is also illustrated in FIG. 1A, but not inFIG. 3A, CPU 32 is connected to host/PCI bridge 36 by CPU local bus 34,in a conventional manner; system memory 40 is connected to host/PCIbridge 36 by memory bus 38, in a conventional manner; and SCSI HBA 44,NIC 46 and graphics adapter 48 are connected to host/PCI bridge 36 byPCI bus 42, in a conventional manner. FIG. 3A also shows the same videomonitor 62, the same networks 60 and the same SCSI bus 50 as are shownin FIGS. 1A and 2A, along with the same SCSI DISK 52 and the same tapestorage device 54, which are again shown as being connected to SCSI bus50. Other devices may also be connected to SCSI bus 50. Thus, graphicsadapter 48 (not shown in FIG. 3A) is connected to video monitor 62 in aconventional manner; NIC 46 (not shown in FIG. 3A) is connected to datanetworks 60 in a conventional manner; and SCSI HBA 44 (not shown in FIG.3A) supports SCSI bus 50 in a conventional manner.

FIG. 3A also shows VMkernel 100B, which, except as described below, maybe substantially the same as kernel 100 of FIG. 2A. Thus, VMkernel 100Bincludes resource manager 102B, which, except as described below, may besubstantially the same as resource manager 102 of FIG. 2A. Note thatVMKernel 100B also includes PCI resource manager 104. As will beexplained below, PCI resource manager 104 manages the resources of PCIpassthrough module 204 that is created in accordance with one or moreembodiments of the present invention, to provide functions such ascreating and managing a configuration register for PCI passthroughdevices.

FIG. 3A also shows VMM 200B, which, except as described below, may besubstantially the same as VMM 200 of FIG. 2A. Thus, VMM 200B includesvirtual system hardware 330B, which includes a set of virtual devices202B, which, except as described below, may be substantially the same asvirtual devices 202 of FIG. 2A. Note also that VMM 200B includes PCIpassthrough module 204 that is created in accordance with one or moreembodiments of the present invention. PCI passthrough module 204 is asoftware module in VMM 200B as a virtualization module for providing VM300B with direct access to a corresponding physical hardware device. Aswill be explained below in more detail, PCI passthrough module 204advertises hardware devices to appear in the virtual PCI bus hierarchy,provides transparent/non-transparent mapping to hardware devices,handles interrupts from passthrough devices, and serves as a conduit foraccessing the passthrough devices. As shown in FIG. 3A, VMkernel 100Band VMM 200B may generally be referred to as virtualization software150B. Such virtualization software may take a wide variety of otherforms in other implementations of the invention.

FIG. 3A also shows VM 300B, which, except as described below, may besubstantially the same as VMs 300 of FIG. 2A. Thus, VM 300B includes aset of applications 310B, which may be substantially the same as the setof applications 310 of FIG. 2A; OS 320B, which may be substantially thesame as OS 320 of FIG. 2A; a set of drivers 324B, which may besubstantially the same as the set of drivers 320 of FIG. 2A; and systemBIOS 322B, which may be substantially the same as system BIOS 322 ofFIG. 2A. OS 320B, drivers 324B and system BIOS 322B constitute guestsystem software for VM 300B. The guest system software has direct accessto a physical hardware device through PCI passthrough module 204 underresource management by PCI resource manager 104.

As also shown in FIG. 3A, VM 300B includes virtual system hardware 330B,which, except as described below, may be substantially the same asvirtual system hardware 330 of FIG. 2A. FIG. 3B shows aspects of virtualsystem hardware 330B that are most relevant to one or more embodimentsof the present invention. Again, for the example virtual computer systemof FIGS. 3A and 3B, virtual system hardware 330B is functionally similarto the underlying physical system hardware 30, although, for othervirtual computer systems, the virtual system hardware may be quitedifferent from the underlying physical system hardware. Thus, FIG. 3Bshows processor (CPU or Central Processing Unit) 332B, host/PCI bridge336B, system memory 340B, NIC 346B, and graphics adapter 348B, each ofwhich may be implemented as conventional devices, substantially similarto the corresponding devices in the underlying physical hardware 30.Processor 332B appears to be connected to host/PCI bridge 336B in aconventional manner, as if by CPU local bus 334B; system memory 340Bappears to be connected to host/PCI bridge 336B in a conventionalmanner, as if by memory bus 338B; and SCSI HBA 344B, NIC 346B andgraphics adapter 348B appear to be connected to host/PCI bridge 336B ina conventional manner, as if by PCI bus 342B. Graphics adapter 348Bappears to be connected to conventional video monitor 362B in aconventional manner; and NIC 346B appears to be connected to one or moreconventional data networks 360B in a conventional manner.

As shown in FIG. 3B, virtual system hardware 330B includes PCIpassthrough device for HBA 399 that is connected to PCI bus 342B. Inaccordance with one or more embodiments of the present invention, PCIpassthrough device 399 in FIG. 3B is a virtualization of SCSI HBA 44that controls SCSI disk 52, but it is virtually connected to virtual PCIbus 342B so that VM 300B can have direct access to SCSI HBA 44 throughPCI passthrough device 399 as if SCSI HBA 44 is directly connected to VM300B.

To expose a physical hardware device such as SCSI HBA 44 to VM 300B, PCIpassthrough module 204 (refer to FIG. 3A) obtains actual PCI resourceinformation (e.g. vendor id, class id, subclass, base address registervalues, real IRQ/vector assigned to the device, etc.) from PCI resourcemanager 104 (refer to FIG. 3A) for the corresponding physical hardwaredevice (e.g., SCSI HBA 44). Once the PCI resource information isobtained, PCI passthrough module 204 sets up virtual PCI device (PCIpassthrough device) 399 that contains the configuration informationderived from the original physical hardware device (e.g., SCSI HBA 44).PCI passthrough device 399 is hooked up to virtual PCI bus 342B that isvisible to guest software 320B. As part of the process of setting up PCIpassthrough device 399, a callback is registered to handle the PCIconfiguration cycle, so that when guest BIOS 322B or guest OS 320Bperforms PCI configuration access, PCI passthrough module 204 getsnotified. As will be explained below with reference to FIGS. 4A and 4B,when access to the BAR registers for PCI passthrough device 399 is made,the virtual PCI subsystem is requested to allocate virtual port/memorymapped IO space. The size of the memory mapped regions is derived fromthe physical resource information obtained from PCI resource manager 104of VMKernel 100B. When guest OS 320B accesses PCI passthrough device 399through virtual PCI bus 324B, in reality, guest OS 320B is accessingunderlying physical hardware device 44 if guest OS 320B doesport-mapped/memory-mapped I/O to a location contained in the BAR of thecorresponding hardware device.

FIG. 3C illustrates a set of virtual PCI configuration registers for thePCI passthrough device, according to one embodiment of the presentinvention. The PCI configuration registers of FIG. 3C have substantiallythe same structure as PCI configuration register 45 of FIG. 1B andvirtual PCI configuration register 345 of FIG. 2C. PCI passthroughconfiguration registers 347 include Vendor ID register 347A, Device IDregister 347B, Command register 347C, Status register 347D, Revision IDregister 347E, Class Code register 347F, Cache Line Size register 347G,Latency Timer register 347H, Header Type register 347I, BIST register347J, Base Address 0 register 347K, Base Address 1 register 347L, BaseAddress 2 register 347M, Base Address 3 register 347N, Base Address 4register 347O, Base Address 5 register 347P, CardBus CIS Pointerregister 347Q, Subsystem Vendor ID register 347R, Subsystem ID register347S, Expansion ROM Base Address register 347T, first reserved register347U, second reserved register 347V, Interrupt Line register 347W,Interrupt Pin register 347X, Min_Gnt register 347Y and Max_Lat register347Z. FIG. 3C also shows Virtual PCI Extended Configuration Space(including a set of Device-Specific Registers) 347AA.

Some of the contents of PCI passthrough configuration registers 347 maybe different from the contents of configuration register 45 of thecorresponding actual physical hardware device. For example, commandregister 347C, status register 347D, BAR registers 347K through 347P,and expansion ROM base address 347T, and device specific register 347AAmay be different from the content of corresponding registers 45 of thecorresponding actual physical hardware device. PCI passthroughconfiguration register 347 is created and maintained by PCI passthroughmodule 204 so that VMs 300 have direct access to the underlying actualphysical device by having access to configuration register 347 ofpassthrough device 399.

FIG. 4A is an interaction diagram illustrating how a PCI passthroughdevice is created and used in non-trap mode, according to one embodimentof the present invention. Referring to FIGS. 3B and 4A, to create PCIpassthrough device 399 corresponding to an underlying hardware device(e.g., SCSI HBA 44), (step 402) VMM PCI passthrough module 204 requests402 VMKernel PCI resource manager 104 for configuration registerinformation corresponding to the underlying hardware device. (step 404)VMKernel PCI resource manager 104, in turn, forwards such request toVMKernel resource manage 102B that actually manages the configurationregisters of the hardware devices. (step 406) VMKernel resource manager102B returns the configuration register information to VMKernel PCIresource manager 104, which information is then passed on to VMM PCIpassthrough module 204. (step 408) VMM PCI passthrough module 204creates PCI passthrough device 399 corresponding to the hardware device(SCSI HBA 44) by creating virtual PCI configuration registers 347 forPCI passthrough device 399, where virtual PCI configuration registers347 resemble configuration register information 45 of the underlyinghardware device (SCSI HBA 44), with additional changes as explainedabove with reference to FIG. 3C. (step 410) VMM PCI passthrough module204 then notifies VMM 200B of the creation of PCI passthrough device399.

Once PCI passthrough device 399 is created, it can be accessed inread/write operations in either trap mode or non-trap mode. Theembodiment illustrated in FIG. 4A uses non-trap mode. Specifically,(step 412) when guest OS 320B issues a memory-mapped/port-mapped I/Ooperation with a guest physical address (GPA) contained within the BAR(Base Address Register) of PCI passthrough device 399, (step 414) VMMPCI passthrough device 204 maps the guest physical address (hereinafter,“GPA”) with a corresponding machine address (hereinafter, “MA”) (guestPCI address to host PCI address mapping). (step 418) VMM 200B performsI/O operation 418 with the MA by accessing actual physical device 44(e.g., SCSI HBA) with the MA, (step 420) to complete the R/W operation.Once the GPA to MA translation is set up by VMM PCI passthrough module204, no further intervention by VMM PCI passthrough module 204 isneeded. (step 422) Subsequent I/O operations with a GPA within the BARof the physical device (step 424) can be performed directly withoutintervention from VMM 200B and VMM PCI passthrough module 204, resultingin faster direct access to the device (e.g., HBA 44). Therefore, innon-trap mode, guest OS 320B of the virtualized computer system accessesphysical device 44 directly, in contrast to conventional virtualizedcomputer systems.

FIG. 4B is an interaction diagram illustrating how a PCI passthroughmodule is created and used in a trap mode, according to one embodimentof the present invention. The embodiment shown in FIG. 4B issubstantially the same as the non-trap mode embodiment of FIG. 4A insteps 402 through 412, except that steps 452 through 456 in FIG. 4Breplace steps 414 through 424 in FIG. 4A. Specifically, (step 412) whenguest OS 320B issues a memory-mapped/port-mapped I/O operation with aguest physical address (GPA) contained within the BAR (Base AddressRegister) of PCI passthrough device 399, VMM PCI passthrough module 204issues proxy I/O operation 452, with an MA corresponding to the GPA,directly to hardware device 44 which performs the I/O operation. (step456) VMM PCI passthrough module 204 notifies guest O/S 320B of thecompletion of the I/O operation. As is clear from FIG. 4B, in the trapmode, VMM PCI passthrough module 204 “traps” I/O operations fromguest/OS 320B to physical device 44. Thus, guest O/S 320B has directaccess to physical device 44 through VMM PCI passthrough module 204.Trap mode is beneficial when, for example, the behavior of physicaldevice 44 is to be monitored by VMM 200B for debugging purposes.

An interesting problem arises when physical device 44 is exposed to VMs300. When device drivers 324B of guest OS 320B communicate with physicaldevice 44 to perform I/O, device drivers 324B specify the guest physicaladdress (GPA) for the data transfer. However, that GPA may no longer bea valid address since the mapping between GPA and MA could have changed,or some other VM 300B could be running, etc. Thus, physical device 44needs a valid MA that backs the GPA specified by device drivers 324B.FIGS. 5A-5D below illustrate various methods to obtain DMA address(es)of I/O operations with PCI passthrough device 399.

FIG. 5A is an interaction diagram illustrating I/O operation in the PCIpassthrough device using callbacks for I/O mapped accesses, according toone embodiment of the present invention. (step 502) When guest driver324B in guest OS 320B makes I/O request 502 to VMM PCI passthroughmodule 204 with a GPA corresponding to PCI passthrough device 399 in I/Orequest 502, (step 504) VMM PCI passthrough module 204 decodes the I/Orequest 502 and replaces the GPA in I/O request 502 with an MAcorresponding to underlying hardware device 44. (step 506) VMM PCIpassthrough module 204 sends an I/O request with the substituted MA tophysical device 44, and (step 508) physical device 44 completes DMAusing the MA contained in the I/O request of step 506 and notifies guestdriver 324B. The method of FIG. 5A requires that VMM PCI passthroughmodule 204 trap all I/O requests to PCI passthrough device 399, whichmay affect performance. In addition, the method of FIG. 5A requires thatVMM PCI passthrough module 204 understand and decode I/O requests tohardware device 44. Otherwise, there is no other virtualizationoverhead.

FIG. 5B is an interaction diagram illustrating I/O operation in a PCIpassthrough device using driver change, according to one embodiment ofthe present invention. The method of FIG. 5B trusts guest driver 324B inguest OS 320B, and modifies the driver code so that guest driver 324Bmakes the I/O request with an MA rather than the GPA. Referring to FIG.5B, (step 510) first guest driver 324B requests DMA cache 590 (includedin guest OS 320B) for an MA corresponding to the GPA in the I/O request.(step 512) If the MA corresponding to the GPA is not available in DMAcache 590, resulting in a miss in DMA cache 590, (step 514) DMA cache590 makes a hypervisor call to VMM 200B to obtain the MA correspondingto the GPA, and (step 516) VMM 200B returns the corresponding MA to DMAcache 590. If the MA corresponding to the GPA is available in DMA cache590, steps 512, 514, and 516 are skipped. In step 518, DMA cache 590returns the MA corresponding to the GPA to guest driver 324B. Then,(step 520) guest driver 324B makes an I/O request to physical device 44directly using the MA, and (step 522) physical device 44 completes DMAusing the MA in the request of step 520 and returns the results to guestdriver 324B. Then, (step 524) guest driver 324B releases the MA to GPAmapping back to DMA cache 590, and (step 526) the process returns toguest driver 324B for the next I/O request. In the method of FIG. 5B, ahashing can be implemented for repeated GPA to MA mappings. The methodof FIG. 5B is somewhat intrusive in the sense that modification of guestdriver 324B is needed, but a significant performance gain can beachieved thanks to direct access to physical device 44.

FIG. 5C is an interaction diagram illustrating I/O operation in a PCIpassthrough device using on-demand mapping with an I/O MMU (Input/OutputMemory Management Unit), according to one embodiment of the presentinvention. The method of FIG. 5C is efficient and less intrusive than,for example, the method in FIG. 5B, but it only works for devices thatcan set up address translation (I/O MMU) in the physical device suchthat an interrupt/exception can be generated for a missing mapping fromGPA to MA. Referring to FIG. 5C, (step 530) guest driver 324B makes anI/O request to hardware device 44 with a GPA corresponding to PCIpassthrough device 399 contained in the request. (step 532) Hardwaredevice 44 issues a DMA request with the GPA contained in the I/Orequest. I/O MMU (Input/Output Memory Management Unit) 550 (which may beincluded in HBA 44, for example) intercepts the DMA request to performGPA to MA mapping before the DMA request is forwarded to memory. (step534) If the GPA to MA mapping is missing in I/O MMU 550, (step 536) aninterrupt/exception is issued to VMM 200B through, for example, amessage signaled interrupt (MSI) on PCI bus 342B, (step 539) to set upthe mapping from the specified GPA to the corresponding MA. Then, (step542) VMM 200B acknowledges the interrupt to I/O MMU 550. After I/O MMU550 determines the correct GPA to MA mapping, (step 544) I/O MMU 550forwards the DMA request with the MA to memory controller 560 (which isincluded in system hardware 30). Memory controller 560 performs the DMAoperation, and (step 546) informs hardware device 44 that the DMA R/Woperation is complete. (step 548) Hardware device 44 informs guestdriver 324B that the I/O request by physical device 44 is complete. Notethat, when VMM PCI passthrough module 204 wants to reclaim the MA, itcan issue a request to I/O MMU 550 to flush its memory mapping.

FIG. 5D is an interaction diagram illustrating I/O operation in a PCIpassthrough module using identity mapping, according to one embodimentof the present invention. For VM 300B in this embodiment, the GPA and MAare identity-mapped such that each GPA corresponds to the same MA. Forexample, GPA 0 corresponds to MA 0. In this case, VM 300B (guest driver324B) can use the GPA to make an I/O request to physical device 44,because the GPA and MA are the same and there is no need to obtain GPAto MA mapping. Thus, referring to FIG. 5D, (step 551) guest driver 324Bissues an I/O request to physical device 44, with a GPA that isidentical to the MA. (step 552) physical device 44 just completes theDMA using the GPA. The embodiment of FIG. 5D allows PCI passthroughdevices 399 to operate without requiring driver changes or I/O MMUs.

Another interesting problem arises when physical device 44 is exposed toVMs 300B. Specifically, when hardware device 44 wants to notify devicedriver 324B of guest OS 320B, it generates an interrupt. However, in avirtual machine environment, guest OS 320B that is communicating withphysical device 44 may not be running at the time of interruptgeneration. FIGS. 6, 7A, and 7B illustrate various methods of handlinginterrupts in PCI passthrough device 399.

FIG. 6 is an interaction diagram illustrating interrupt handling in aPCI passthrough module using physical I/O APIC (Advanced ProgrammableInterrupt Controller), according to one embodiment of the presentinvention. (step 602) When hardware device 44 generates a physicalinterrupt, (step 604) VMKernel PCI module 104 first masks the I/O APICline, and (step (606) issues a physical EOI (End of Interrupt) tophysical local APIC 601 (which may be part of the CPU 32)—the I/O APICline is a shared interrupt line. Step 604 is necessary to enable sharingof the I/O APIC line, and to prevent interrupt storms. Then, (step 608)VMKernel PCI module 104 posts a monitor action to VMM PCI passthroughmodule 204, which, in turn, (step 610) issues a virtual interrupt toguest O/S 320B—the virtual corresponds to the physical interruptgenerated at step 602. (step 612) Guest O/S 320B executing an interruptservice routine. From the perspective of guest OS 320B and device 44,(step 613) the interrupt is now complete. (step 614) Guest O/S 320B alsoissues virtual EOI 614 to virtual local APIC 619 (which may be part ofvirtual CPU 332B), by writing to the virtual local APIC's EOI register.VMM PCI passthrough module 204 traps access to the local APIC's EOIregister, and determines that there is a physical interrupt with an I/OAPIC that needs to be unmasked. Thus, (step 616) VMM PCI passthroughmodule 204 makes a function call to VMKernel PCI module 104 to unmaskthe interrupt. In response, (step 618) VMKernel PCI module 104 unmasksthe I/O APIC line by mapping the I/O APIC's physical address andmanipulating the interrupt vector's entry directly.

The method of FIG. 6 has some inefficiency, in that it has interruptlatency due to the need for masking and unmasking the shared interruptline of the I/O APIC. Also, if a physical interrupt line is shared bymultiple devices, it is possible that the virtualized computer systemmay deadlock if the system tries to service some other request while theinterrupt line is masked. FIGS. 7A and 7B illustrate a method thathandles interrupt in PCI passthrough devices with lower interruptlatencies and without the need for masking interrupt lines by using MSI(Message Signaled Interrupts) or MSI-X defined in the PCI local busspecification to generate non-shared, edge-triggered interrupts that canbe programmed and acknowledged in a device-independent manner throughthe PCI configuration space. The method of FIGS. 7A and 7B can preventan interrupt storm, avoid potential deadlocking, and provide fastturnaround time in handling interrupts.

FIG. 7A is an interaction diagram illustrating interrupt handling in aPCI passthrough module using a physical MSI/MSI-X device with virtualI/O APIC that is level triggered, according to one embodiment of thepresent invention. In the embodiment of FIG. 7A, the allocation of theMSI/MSI-X is handled by VMKernel PCI module 104 in a manner opaque toguest OS 320B. Referring to FIG. 7A, (step 603) when hardware device 44generates a physical interrupt (MSI) to VMKernel PCI module 104, (step606) VMKernel PCI module 104 issues a physical EOI (End of Interrupt) tophysical local APIC 601. Then, (step 608) VMKernel PCI module 104 postsa monitor action to VMM PCI passthrough module 204, which, in turn,(step 610) issues a virtual interrupt to guest O/S 320B—the virtualinterrupt corresponding to the physical interrupt of step 603. (step612) guest O/S 320B executes the interrupt service routine, and (step613) notifies physical device 44 that the interrupt has been completed.Also, (step 614) guest O/S 320B issues a virtual EOI to virtual localAPIC 619 by writing to the local APIC's EOI register. There is a smallwindow from the time the physical device interrupt is acknowledged atstep 613 by guest O/S 320B and virtual EOI of step 614, during whichanother physical interrupt may be generated. This situation is handledcarefully to prevent lost interrupts by noting that another interrupthas been received while the previous level virtual interrupt of step 610was still asserted and not de-asserting the interrupt level in this caseon the virtual EOI of step 614.

FIG. 7B is an interaction diagram illustrating interrupt handling in aPCI passthrough module using a physical MSI/MSI-X device with virtualMSI/MSI-X, according to one embodiment of the present invention. Theembodiment of FIG. 7B passes through the MSI/MSI-X capability to guestOS 320B in the virtual device's PCI configuration space 347 withouttransitioning to VMKernel PCI module 104. Referring to FIG. 7B, (step605) physical device 44 generates a physical interrupt (MSI) to VMM PCIpassthrough module 204. (step 609) VMM PCI passthrough module 204recognizes the MSI interrupt, (step 611) issues a physical EOI tophysical local APIC 601, and (step 610) issues a virtual interrupt 610to guest O/S 320B—the virtual interrupt corresponding to the physicalinterrupt of step 605. (step 612) Guest O/S 320B executes the interruptservice routine, and (step 613) notifies physical device 44 that theinterrupt has been completed. Also, (step 614) guest O/S 320B issues avirtual EOI to virtual local APIC 619 by writing to the local APIC's EOIregister. The embodiment of FIG. 7B would be useful when more operatingsystems implement MSI/MSI-X.

Although the embodiment described above relates to a specific physicalcomputer system, having a specific hardware platform and configuration,and a specific software platform and configuration, further embodimentsof the present invention may be implemented in a wide variety of otherphysical computer systems. In addition, although the embodimentdescribed above relates to a specific virtual computer systemimplemented within the physical computer system, further embodiments ofthe present invention may be implemented in connection with a widevariety of other virtual computer systems. In further addition, althoughthe embodiment described above relates to a specific physical device,further embodiments of the present invention may be implemented inconnection with a wide variety of other physical devices. In particular,although the embodiment described above relates to a SCSI HBA cardinterfacing to a PCI bus for providing a VM with direct access to a SCSIdevice/HBA, further embodiments of the present invention may beimplemented in connection with a wide variety of other physical devices.For example, embodiments may be implemented in connection with adifferent physical device that also interfaces to a PCI bus, but thatimplements a different function, such as a fiber channel HBA, forexample. Alternatively, further embodiments may be implemented inconnection with a physical device that interfaces with a different typeof bus, or that interfaces with the physical computer system in someother way, and that implements any of a variety of functions.

Upon reading this disclosure, those of ordinary skill in the art willappreciate still additional alternative structural and functionaldesigns for providing a virtual machine with direct access to physicalhardware devices. For example, embodiments of the present invention arenot limited to exposing PCI-devices to a guest operating system, but canbe used to expose other hardware devices connected to a virtualizedcomputer system through other types of communication interfaces. Thus,while particular embodiments and applications of the present inventionhave been illustrated and described, it is to be understood that theinvention is not limited to the precise construction and componentsdisclosed herein. Various modifications, changes and variations whichwill be apparent to those skilled in the art may be made in thearrangement, operation and details of the method and apparatus of thepresent invention disclosed herein without departing from the spirit andscope of the invention as defined in the appended claims.

One or more embodiments of the present invention may be implemented asone or more computer programs or as one or more computer program modulesembodied in one or more computer readable media. The computer readablemedia may be based on any existing or subsequently developed technologyfor embodying computer programs in a manner that enables them to be readby a computer. For example, the computer readable media may comprise oneor more CDs (Compact Discs), one or more DVDs (Digital Versatile Discs),some form of flash memory device, a computer hard disk and/or some formof internal computer memory, to name just a few examples. An embodimentof the invention, in which one or more computer program modules isembodied in one or more computer readable media, may be made by writingthe computer program modules to any combination of one or more computerreadable media. Such an embodiment of the invention may be sold byenabling a customer to obtain a copy of the computer program modules inone or more computer readable media, regardless of the manner in whichthe customer obtains the copy of the computer program modules. Thus, forexample, a computer program implementing an embodiment of the inventionmay be purchased electronically over the Internet and downloadeddirectly from a vendor's web server to the purchaser's computer, withoutany transference of any computer readable media. In such a case, writingthe computer program to a hard disk of the web server to make itavailable over the Internet may be considered a making of the inventionon the part of the vendor, and the purchase and download of the computerprogram by a customer may be considered a sale of the invention by thevendor, as well as a making of the embodiment of the invention by thecustomer. Moreover, one or more embodiments of the present invention maybe implemented wholly or partially in hardware, for example and withoutlimitation, in processor architectures intended to provide hardwaresupport for VMs.

1. In a virtualized computer system in which a guest operating systemruns on a virtual machine of a virtualized computer system and hasdirect access to a hardware device coupled to the virtualized computersystem via a communication interface, a computer implemented method ofhandling interrupts from the hardware device to the guest operatingsystem, the method comprising: receiving a physical interrupt from thehardware device on a shared interrupt line of an interrupt controller,the physical interrupt forwarded to a virtual machine (VM) kernel;masking, by the VM kernel, the shared interrupt line of the interruptcontroller; issuing a physical end of interrupt (EOI) in response to themasking of the shared interrupt line of the interrupt controller, thephysical EOI issued by the VM kernel; generating a virtual interruptcorresponding to the physical interrupt to the guest operating system;and the guest operating system executing an interrupt service routinecorresponding to the virtual interrupt.
 2. The method of claim 1,wherein generating the virtual interrupt further comprising: forwardingthe generated virtual interrupt to the guest operating system through avirtual local Advanced Programmable Interrupt Controller (APIC).
 3. In avirtualized computer system in which a guest operating system runs on avirtual machine of a virtualized computer system and has direct accessto a hardware device coupled to the virtualized computer system via acommunication interface, the virtualized computer system havingvirtualization software that includes a virtual machine (VM) kernel anda virtual machine monitor (VMM), a computer implemented method ofhandling interrupts from the hardware device to the guest operatingsystem, the method comprising: receiving a physical interrupt from thehardware device on a non-shared interrupt line of an interruptcontroller, the physical interrupt communicated directly to apassthrough module of the VMM without transitioning to the VM kernel;issuing a physical end of interrupt (EOI) in response to receiving thephysical interrupt from the hardware device, the physical EOI issued bythe passthrough module of the VMM; generating a virtual interruptcorresponding to the physical interrupt to the guest operating system;and the guest operating system executing an interrupt service routinecorresponding to the virtual interrupt.
 4. The method of claim 3,wherein generating the virtual interrupt further comprising: forwardingthe generated virtual interrupt to the guest operating system through avirtual local Advanced Programmable Interrupt Controller (APIC).
 5. Themethod of claim 3, further comprising the guest operating system issuinga virtual end of interrupt (EOI) responsive to executing an interruptservice routine.
 6. For a virtualized computer system in which a guestoperating system runs on a virtual machine of the virtualized computersystem and has direct access to a hardware device coupled to thevirtualized computer system via a communication interface, a computerprogram product stored on a computer readable medium and configured toperform a computer-implemented method of handling interrupts from thehardware device to the guest operating system, the method comprising:receiving a physical interrupt from the hardware device on a sharedinterrupt line of an interrupt controller, the physical interruptprovided to a virtual machine (VM) kernel; masking, by the VM kernel,the shared interrupt line of the interrupt controller; issuing aphysical end of interrupt (EOI) in response to the masking of the sharedinterrupt line of the interrupt controller, the physical EOI issued bythe VM kernel; generating a virtual interrupt corresponding to thephysical interrupt to the guest operating system; and the guestoperating system executing an interrupt service routine corresponding tothe virtual interrupt.
 7. The computer program product of claim 6,wherein the method further comprises: forwarding the generated virtualinterrupt to the guest operating system through a virtual local AdvancedProgrammable Interrupt Controller (APIC).
 8. For a virtualized computersystem in which a guest operating system runs on a virtual machine ofthe virtualized computer system and has direct access to a hardwaredevice coupled to the virtualized computer system via a communicationinterface, the virtualized computer system having virtualizationsoftware that includes a virtual machine (VM) kernel and a virtualmachine monitor (VMM), a computer program product stored on a computerreadable medium and configured to perform a computer-implemented methodof handling interrupts from the hardware device to the guest operatingsystem, the method comprising: receiving a physical interrupt from thehardware device on a non-shared, edge-triggered interrupt line of aninterrupt controller, the physical interrupt communicated directly to apassthrough module of the VMM without transitioning to the VM kernel;issuing a physical end of interrupt (EOI) in response to receiving thephysical interrupt from the hardware device, the physical EOI issued bythe passthrough module of the VMM; generating a virtual interruptcorresponding to the physical interrupt to the guest operating system;and the guest operating system executing an interrupt service routinecorresponding to the virtual interrupt.
 9. The computer program productof claim 8, wherein the method further comprises: forwarding thegenerated virtual interrupt to the guest operating system through avirtual local Advanced Programmable Interrupt Controller (APIC).
 10. Thecomputer program product of claim 8, wherein the method furthercomprises: the guest operating system issuing a virtual end of interrupt(EOI) responsive to executing an interrupt service routine.
 11. Avirtualized computer system in which a guest operating system runs on avirtual machine of the virtualized computer system and has direct accessto a hardware device coupled to the virtualized computer system via acommunication interface, the virtualized computer system including astorage device storing computer instructions configured to perform acomputer-implemented method of handling interrupts from the hardwaredevice to the guest operating system, and one or more central processingunits for executing the computer instructions, the method comprising:receiving a physical interrupt from the hardware device on a sharedinterrupt line of an interrupt controller, the physical interruptforwarded to a virtual machine (VM) kernel; masking, by the VM kernel,the shared interrupt line of the interrupt controller; issuing aphysical end of interrupt (EOI) in response to the masking of the sharedinterrupt line of the interrupt controller, the physical EOI issued bythe VM kernel; generating a virtual interrupt corresponding to thephysical interrupt to the guest operating system; and the guestoperating system executing an interrupt service routine corresponding tothe virtual interrupt.
 12. The virtualized computer system of claim 11,wherein the method further comprises: forwarding the generated virtualinterrupt to the guest operating system through a virtual local AdvancedProgrammable Interrupt Controller (APIC).
 13. A virtualized computersystem in which a guest operating system runs on a virtual machine ofthe virtualized computer system and has direct access to a hardwaredevice coupled to the virtualized computer system via a communicationinterface, the virtualized computer system having virtualizationsoftware that includes a virtual machine (VM) kernel and a virtualmachine monitor (VMM), the virtualized computer system including astorage device storing computer instructions configured to perform acomputer-implemented method of handling interrupts from the hardwaredevice to the guest operating system, and one or more central processingunits for executing the computer instructions, the method comprising:receiving a physical interrupt from the hardware device on a non-sharedinterrupt line of an interrupt controller, the physical interruptcommunicated directly to a passthrough module of the VMM withouttransitioning to the VM kernel; issuing a physical end of interrupt(EOI) in response to receiving the physical interrupt from the hardwaredevice, the physical EOI issued by the passthrough module of the VMM;generating a virtual interrupt corresponding to the physical interruptto the guest operating system; and the guest operating system executingan interrupt service routine corresponding to the virtual interrupt. 14.The virtualized computer system of claim 13, wherein the method furthercomprises: forwarding the generated virtual interrupt to the guestoperating system through a virtual local Advanced Programmable InterruptController (APIC).
 15. The virtualized computer system of claim 13,wherein the method further comprises: the guest operating system issuinga virtual end of interrupt (EOI) responsive to executing an interruptservice routine.